The error matcher (adapter_runner.rb#matches_patterns?) does case-insensitive
substring/regex matching against both the full error text and the extracted core
message. Patterns only need to capture the semantic essence of the error.

The recorded patterns embedded the input template verbatim, e.g.

  'Liquid syntax error: Expected end_of_string but found close_round in "x = x )"'

That overfits to liquid-ruby's exact wording AND to the exact template text,
which means any implementation with slightly different quoting/formatting fails.

Trim 1901 patterns down to their semantic core:

  'Expected end_of_string but found close_round'

This matches the existing convention in specs/liquid_ruby/strict_rejects_lax_syntax.yml
(short substrings like 'but found pipe', 'Expected close_square').

Result: 80 unique patterns, max length 95 chars (was 1901 unique, often >100).
Verified against liquid_ruby adapter: 1791/1901 specs match correctly; the 110
remaining failures are specs whose enforcement requires strict2_parsing.